Minutes, IBIS Quality Committee

28 Apr 2009

11-12 AM EST (8-9 AM PST)

ROLL CALL
  Adam Tambone
* Anders Ekholm, Ericsson
  Barry Katz, SiSoft
  Benny Lazer
  Benjamin P Silva
  Bob Cox, Micron
* Bob Ross, Teraspeed Consulting Group
  Brian Arsenault
  David Banas, Xilinx
  Eckhard Lenski, Nokia Siemens Networks
  Eric Brock
* Guan Tao, Huawei Technologies
  Gregory R Edlund
  Hazem Hegazy
  Huang Chunxing, Huawei Technologies
  John Figueroa
  John Angulo, Mentor Graphics
  Katja Koller, Nokia Siemens Networks
  Kevin Fisher
  Kim Helliwell, LSI Logic
  Lance Wang, IOMethodology
  Lynne Green
* Mike LaBonte, Cisco Systems
  Mike Mayer, SiSoft
* Moshiul Haque, Micron Technology
  Muniswarareddy Vorugu, ARM Ltd
  Pavani Jella, TI
  Peter LaFlamme
  Randy Wolff, Micron Technology
  Radovan Vuletic, Qimonda
  Robert Haller, Enterasys
  Roy Leventhal, Leventhal Design & Communications
  Sherif Hammad, Mentor Graphics
  Todd Westerhoff, SiSoft
  Tom Dagostino, Teraspeed Consulting Group
  Kazuyoshi Shoji, Hitachi
  Sadahiro Nonoyama
  Liqun, Huawei

Everyone in attendance marked by *

NOTE: "AR" = Action Required.

-----------------------MINUTES ---------------------------
Mike LaBonte conducted the meeting.

Call for patent disclosure:

- No one declared a patent.

AR Review:

- Mike look into MeetingPlace issues
  - Mike will use WebEx for our next meeting
  - MeetingPlace will be the backup

New items:

Should we file an IBISCHK bug report for a dV against I/V check?
- We decided not to do this immediately

[Ramp] dV checks:
- Mike: Possible checks are:
  - dV against supply voltage
  - dV against V/T endpoints
  - dV against I/V
- We voted unanimously to replace 5.5.4 with a dV vs. I/V
- Moshiul: Which of these is the central reference?
  - When discrepancies are found, either could be wrong
- Anders: The old 5.5.4 checked against I-V
- Bob: We can synthesize V/T tables based on Ramp to do this in IBISCHK
  - The idea is to create fake waveforms with [Ramp] fixtures
  - Just one bogus point is needed
  - This forces IBISCHK to print the correct voltage calculated from I/V
- How much accuracy to require:
  - Anders: This should be much more accurate than V/T endpoint checks
  - Bob: Taking 60% of a value reduces the error magnitude
  - Mike: Taking a difference doubles the error magnitude
    - I/V interpolation will add error too
- Bob: The error limit should be 10%
  - Mike: How about 1% ?
  - Bob: Tables may not have enough significant digits
  - Anders: How about 5%
- Mike: We should set an accuracy criteria based on simulation results
  - But dV is not used for anything
  - An error of 10mV for a 2.5V part would be 4%
- Anders: This will show if someone has tweaked [Voltage Range]
- Mike: This check can detect poor I/V resolution
  - Bob: There can be DC convergence issues
  - Mike: And I/V test fixtures are difficult to simulate
- The values calculated from I-V will be the reference for error percentage

Next meeting: 05 May 2009 11-12 AM EST (8-9 AM PST)

Meeting ended at 12:08 PM Eastern Time.